| 1. |
Customer Relationship Management: Evolution, Not Revolution ( Pages)
by Jane Affleck
Sep 24, 2007
Abstract : Customer relationship management (CRM) can be a tool for positive change in businesses' operations. Or CRM can—unintentionally—cause a host of problems, from lost employee time to lost customer data. But with the right information, implementing CRM allows evolution without the upset of revolution.
|
| 2. |
Descartes Evolution Yields Revenue Growth But No Profits ( Pages)
by Steve McVey
Dec 1, 1999
Abstract : Descartes Systems Group recently announced its financial results for the third quarter ended October 31, 1999. Revenues were $10.5 million, an increase of 7% over last quarter, but a decrease of 16% from the same period last year. Descartes attributes the renewed revenue growth to its successful evolution into a provider of customer fulfillment network optimization software. In contrast to its revenues, Descartes posted a net loss of $4 million, suggesting that it has not yet fully recovered from an acquisition spree in 1997 and 1998.
|
| 3. |
Fourth Shift's evolution Within SoftBrands' DemandStream Part 2: Challenges and User Recommendations ( Pages)
by P.J. Jakovljevic
Oct 1, 2002
Abstract : In addition to putting the problems of blending two former independent organizations together behind, the company is still entangled in figuring out how best to bring different technologies and industrial experiences to bear. Further, the new company is left with multiple products whose brand recognition is quite low given recent re-branding effort that may be even more impeded by SoftBrands/Fourth Shift/evolution brand confusion (not to mention the plethora of hospitality products).
|
| 4. |
Enterprise Applications--The Genesis and Future, Revisited Part One: 1960s--Pre-Computer Era ( Pages)
by P.J. Jakovljevic
Mar 31, 2004
Abstract : Knowing the history and evolution of enterprise applications is essential to understanding their current use and future developments. Each step in the evolution of the software is built on the fundamentals and principles developed within the previous one, which holds true for the contemporary phase of the 2000s as well.
|
| 5. |
The Essential ERP - Its Genesis & Future ( Pages)
by P.J. Jakovljevic
Dec 25, 2000
Abstract : Knowing the history and evolution of ERP is essential to understanding its current application and its future developments. Each step in the evolution of ERP is built on the fundamentals and principles developed within the previous one.
|
| 6. |
Fourth Shift's evolution Within SoftBrands' DemandStream ( Pages)
by P.J. Jakovljevic
Sep 30, 2002
Abstract : With a set of seemingly complementary products and via a strategy of focusing on customers, astute acquisitions of more complementary software companies and a careful deployment of all resources around the world including product development, sales and customer support, SoftBrands hopes to rise from the ashes of its ill-fated predecessor, AremisSoft.
|
| 7. |
Architecture Evolution: Service-oriented Architecture versus Web Services ( Pages)
by P.J. Jakovljevic
Sep 20, 2006
Abstract : Collaboration and interoperability are critical where multiple business units reside under one larger corporation, or where there is a requirement to integrate the system into a disparate system when a business-to-business or business-to-consumer extension is part of the business model.
|
| 8. |
Architecture Evolution: From Web-based to Service-oriented Architecture ( Pages)
by P.J. Jakovljevic
Sep 19, 2006
Abstract : Traditional enterprise systems have proven difficult to change and extend. The inherent problem of old core code and business logic duplication is part of the reason traditional enterprise resource planning systems have not readily taken to e-commerce.
|
| 9. |
Architecture Evolution: From Mainframes to Service-oriented Architecture ( Pages)
by P.J. Jakovljevic
Sep 18, 2006
Abstract : Product architecture is going to do much more than simply provide the technical functionality, the user interface, and the platform support. It is going to determine whether a product is going to be able to accommodate increasingly evolving user requirements.
|
CART 
